Skip to content

profile: reframe org README as 'Spend controls for Voice AI' - #21

Merged
achris7 merged 1 commit into
mainfrom
profile/spend-controls-voice-ai
Aug 8, 2026
Merged

profile: reframe org README as 'Spend controls for Voice AI'#21
achris7 merged 1 commit into
mainfrom
profile/spend-controls-voice-ai

Conversation

@achris7

@achris7 achris7 commented Aug 8, 2026

Copy link
Copy Markdown
Member

Reframes the org profile around Spend controls for Voice AI per the new positioning, validated against the shipped product.

Kept verbatim: the 3-curl one-turn quickstart (shared X-Floe-Task-Id), the MCP block, the BYOK base_url snippet, and the Marketplace + Framework tables.

Removed: the Roadmap (credit lines / trust record), the wallet/stablecoin/x402 framing, "budget not a balance", and the budget-advisory bullet (docs-only now).

Added: "The problem" (token router ~40% vs 100%, BYOK $0 dashboards), "Three ways in" (platform hooks / BYOK / keyless), and the merged voice recipes.

Accuracy corrections vs the source draft (flagging so you can veto):

  • "200 API credits" → kept "300" — the welcome credit is $3 = 300 credits (the current README already said 300).
  • Dropped the "bland" custom-LLM recipe — Bland has no self-serve custom LLM and no such recipe exists; noted Bland is governed by Reconcile Mode instead.
  • Dropped the "Coverage calculator →" link — no calculator page/tool exists (only the migration guide, which I linked to the real gitbook page).
  • Repos "rows" for recipes rendered as a Voice recipes line (they're cookbook subdirs, not repos), and I listed only the 3 merged on mainpipecat-livekit-reconcile is still on PR #57, so linking /tree/main/... would 404.
  • Dropped the "Start building — pick your path" table to match the new structure — say the word if you want it back.

Latency 38ms p50 / ~180ms p99 verified against latency-overhead.md (keyless rail, live prod).

Summary by CodeRabbit

  • Documentation
    • Updated the README to position Floe as a voice-AI spend-control platform.
    • Added gateway enforcement details and a unified voice-turn quickstart.
    • Documented platform integrations, BYOK, and keyless usage options.
    • Expanded billing examples to cover shared budgets and per-response cost reporting.
    • Added references to Floe Guard and voice recipes.

- New hero + 'The problem' (token router ~40%, BYOK dashboards show $0, the join
  + enforcement; validated 38ms p50 / ~180ms p99 keyless-prod latency).
- 'Three ways in': inside your platform (Vapi/Retell/Bland hooks), BYOK, keyless.
- Remove the Roadmap (credit lines / trust record), the wallet/stablecoin/x402
  framing, 'budget not a balance', and the budget-advisory bullet (docs-only now).
- Keep verbatim: the 3-curl one-turn quickstart, MCP block, BYOK base_url snippet,
  marketplace + framework tables.
- Add merged voice recipes (vapi-custom-llm, retell-custom-llm, vapi-voice-metered).

Accuracy corrections vs the source draft: kept '300 API credits' (not 200);
dropped the non-existent Bland custom-LLM recipe (Bland is reconcile-only) and the
non-existent coverage calculator; linked real gitbook pages.
@coderabbitai

coderabbitai Bot commented Aug 8, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The profile README now presents Floe as a voice-AI spend-control platform. It documents enforcement behavior, a unified voice-turn quickstart, three integration paths, keyless usage, response-cost reporting, and updated repository links.

Changes

Voice-AI spend controls

Layer / File(s) Summary
Positioning and voice quickstart
profile/README.md
The README adds voice-AI spend-control positioning, welcome credits, the problem statement, enforcement details, and response-cost reporting.
Integration paths
profile/README.md
The README documents platform hooks, BYOK routing, and keyless integration with Floe funding and settlement.
Repository overview
profile/README.md
Repository descriptions now emphasize spend controls and metered calls. The README adds floe-guard and voice recipe links and removes the roadmap.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

  • Floe-Labs/.github#14: Updates the same README with overlapping voice-first positioning, quickstart content, and floe-guard references.
  • Floe-Labs/.github#15: Updates the voice quickstart and keyless LLM gateway examples in the same README.

Poem

A rabbit hops where voice turns flow,
With budgets set before costs grow.
One key can guide each call with care,
And metered answers now declare.
New paths and guardrails light the way,
While old roadmaps rest today.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main README change: reframing the organization around spend controls for Voice AI.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch profile/spend-controls-voice-ai

Comment @coderabbitai help to get the list of available commands.

@achris7
achris7 marked this pull request as ready for review August 8, 2026 01:25
Copilot AI lite review requested due to automatic review settings August 8, 2026 01:25

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR reframes the organization profile README around the new positioning “Spend controls for Voice AI”, restructuring the narrative to emphasize multi-vendor cost joining and pre-spend enforcement for voice stacks.

Changes:

  • Replaces the opening positioning and “Why Floe” section with a new “The problem” framing and updated quickstart heading.
  • Adds a “Three ways in” section (platform hooks, BYOK, keyless) and consolidates voice recipes links.
  • Removes roadmap/credit framing and updates repo descriptions to match the new focus.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread profile/README.md
Comment thread profile/README.md

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@profile/README.md`:
- Line 5: Update the README headline and the referenced coverage metrics to use
one consistent cost denominator and accurately describe enforcement modes.
Revise the line-5 claim to qualify pre-call, media-hook, and Reconcile Mode
coverage across Vapi, Retell, Bland, and BYOK; align the LLM percentage in the
line-20 metric with the custom-LLM coverage described near line 66, and clarify
that reconciliation blocks subsequent calls rather than enforcing the full bill
before payment.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 07934437-444d-4534-bf5e-611848c2aa9d

📥 Commits

Reviewing files that changed from the base of the PR and between 4923a61 and 411ead4.

📒 Files selected for processing (1)
  • profile/README.md

Comment thread profile/README.md
@achris7
achris7 merged commit 8b4862d into main Aug 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants